Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Avoid default IP of 0.0.0.0 #369

Merged
merged 1 commit into from
Oct 16, 2024
Merged

Conversation

Ongy
Copy link
Contributor

@Ongy Ongy commented Oct 16, 2024

This default never makes sense, since a connection request to the 0 IP always fails.
The Option mechanism provides a better way of setting an unknown that can easily be detected than abusing a valid but useless IP address.

This default never makes sense, since a connection request to the 0 IP
always fails.
The Option mechanism provides a better way of setting an unknown that
can easily be detected than abusing a valid but useless IP address.
@Ongy
Copy link
Contributor Author

Ongy commented Oct 16, 2024

Let's see if we agree this time :)

@erebe
Copy link
Owner

erebe commented Oct 16, 2024

Like that, I am ok with your change.
Just for me to understand, do you face any real issue with actual behavior, or it is out of purity sake/better error message ?

@Ongy
Copy link
Contributor Author

Ongy commented Oct 16, 2024

Saw it in our logs, tracked it in code, fixed it in code, then realized that we are causing it ourselves and also fixed it in the environment of how it's run.

@Ongy
Copy link
Contributor Author

Ongy commented Oct 16, 2024

In this case it was caused by using a tcp livenessProbe in kubernetes.

Though I think it would generally happen if something tried to send a request directly instead of the CONNECT http verb, which is a more likely mistake people might make.

@erebe
Copy link
Owner

erebe commented Oct 16, 2024

Alright :)

Thank you for the contribution, it is really appreciated !

@erebe erebe merged commit 820cb22 into erebe:main Oct 16, 2024
13 checks passed
jmars pushed a commit to jmars/wstunnel that referenced this pull request Dec 23, 2024
This default never makes sense, since a connection request to the 0 IP
always fails.
The Option mechanism provides a better way of setting an unknown that
can easily be detected than abusing a valid but useless IP address.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants